Match Parameter Keys

Overview

Match Parameter Keys copies the Key Parameter flags (the Key setting in the Inventor Parameter grid) from one component to another. Use it when you want another component to participate in the same key-driven workflows (such as part numbering rules) without changing the numeric/text values of the parameters.

This is especially useful when key parameters drive downstream automation (e.g., a SetPartNumber rule) and you need multiple components to share the same “key-ness” definition while retaining their existing values.

How It Works

Prompts you to pick a source component occurrence (highlighted after selection).
Prompts you to pick a destination component occurrence.
Copies user parameters by name from the source document to the destination document, applying this behavior:
- Copies the Key flag only.
- Does not modify parameter values/expressions.
- Does not create missing parameters in the destination.
Updates the active document after copying.

Usage Instructions

Open the assembly containing the components you want to synchronize.
Click Match Keys in the Configure panel.
Select the source component (the one with the correct key-parameter flags).
Select the destination component (the one that should adopt the same key flags).
If you use key-driven automation (like part numbering), run/refresh your rules as needed.

Troubleshooting

No keys changed: The destination may not have user parameters with the same names as the source.
Only some keys changed: Parameters that can’t be updated due to document state or parameter issues may be skipped.
You expected values to copy too: Match Keys only copies the IsKey flag. Use Match (values) or Match Both (values + keys).
Part numbers still don’t update: Confirm the document has a working SetPartNumber rule and that it uses the key parameters you expect.

Examples

Normalize key parameters for numbering: Copy key flags from a “standard” component into another so both participate in the same part number generation logic.

Keep values, change what’s considered a key: Mark the same fields as keys across multiple components without disturbing existing sizes/options.

Prepare a replacement component: Before swapping a component, ensure the replacement has matching key flags so rules behave consistently.